Fix resource leak in gdk_display_close() under Wayland

When using the gdk_display_close(), the handle to the Wayland compositor was not released. This could cause the consumption of all available handles, preventing other processes from accessing the display.

Fixing this by calling wl_display_disconnect() when releasing the GdkWaylandDisplay object.

Signed-off-by: Julien Ropé <jrope@redhat.com>

diff --git a/gdk/wayland/gdkdisplay-wayland.c b/gdk/wayland/gdkdisplay-wayland.c
index 9be0bacfadc6d3269773c12f2873059f9abbe165..035eec5819ceeba7b3b0c282a03e6513e2678a1c 100644 (file)
--- a/gdk/wayland/gdkdisplay-wayland.c
+++ b/gdk/wayland/gdkdisplay-wayland.c
@@ -755,6 +755,8 @@ gdk_wayland_display_finalize (GObject *object)
 
   g_clear_object (&display_wayland->settings_portal);
 
+  wl_display_disconnect (display_wayland->wl_display);
+
   G_OBJECT_CLASS (gdk_wayland_display_parent_class)->finalize (object);
 }